In SAS Social Network Analysis Server, a social network might be generated for an alert with incorrect-user credentials. The credentials from the previous-user's logon might be used. The issue could happen when integrating with other SAS solutions. Examples include: SAS^® Anti-Money Laundering, SAS^® Enterprise Governance Risk Compliance, and SAS^® Enterprise Case Management. This issue might occur in following use-case:

• User 1 logs on to SAS Anti-Money Laundering.
• Open the funds tracker link for an account/alert, which generates a social network output in the second window.
• User 1 logs off of SAS Anti-Money Laundering.
• User 2 logs on to SAS Anti-Money Laundering.

• Open the funds tracker link for an account/alert. A social network output is generated but it might use User 1 credentials instead of User 2 credentials.

To resolve the issue, follow these steps:

1. Comment out the following block of code in the web.xml file (located in the <Config>\<LevX>\Web\WebAppServer\SASServer8_1\sas_webapps\sas.sso.snaserver.war\WEB-INF directory):

   <filter>
        <filter-name>SanitizingRequestFilter</filter-name>
        <filter-class>
           com.sas.framework.webapp.servlet.SanitizingRequestFilter
        </filter-class>
   </filter>

2. In the same web.xml file, perform these actions:

   •   Uncomment the following block of code:

     <!--
      <filter>
       <filter-name>SanitizingRequestFilter</filter-name>
       <filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class>
          <init-param>
             <param-name>targetBeanName</param-name>
             <param-value>sanitizingRequestFilter</param-value>
          </init-param>
          <init-param>
             <param-name>targetFilterLifecycle</param-name>
             <param-value>true</param-value>
          </init-param>
      </filter>
     -->

   • Add the following new <init-param> element block of code after the line <filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class>

     <init-param>
          <param-name>allowedPostNames</param-name>
          <param-value>snaSheet</param-value>
     </init-param>

3. In the same web.xml file, uncomment the following block of code:

   <!--
        <listener>
           <listener-class>org.jasig.cas.client.session.SingleSignOutHttpSessionListener</listener-class>
        </listener>
   -->

4. To make sure that SAS^® Deployment Manager does not suppress these changes in the future, make the same changes to the <SASHome>\SASSocialNetworkAnalysisMidTier\6.2\Configurable\wars\sas.sso.snaserver\WEB-INF\web.xml.orig file.

5. Uncomment the following block of code in the services-config.xml file (located in the <Config>\<LevX>\Web\WebAppServer\SASServer8_1\sas_webapps\sas.sso.snaserver.war\WEB-INF\spring-config directory):

   <!--
        <import resource="classpath*:META-INF/xss-config.xml" />
   -->

6. In the same services-config.xml file, delete the following line of code:

   <!--this is a little too heavy handed for us at this time-->
7. To make sure that SAS Deployment Manager does not suppress these changes in the future, make the same changes to the services-config.xml file (located in the <SASHome>\SASSocialNetworkAnalysisMidTier\6.2\Static\wars\sas.sso.snaserver\WEB-INF\spring-config\ directory).
8. Restart all the SAS® Web Application Server servers.

Operating System and Release Information